Bumps the engine to @agentage/memory-core@^0.1.3 + @agentage/server-memory@^0.0.3 and turns the two test.skip gaps in the frozen MCP contract tier into live assertions for the new engine behaviors.

Dep bump

• @agentage/memory-core ^0.1.2 -> ^0.1.3, @agentage/server-memory ^0.0.2 -> ^0.0.3 (targeted install; the lock diff touches only these two packages and their subtree, no unrelated churn).

New engine behaviors now asserted

1. Secret refusal: write/edit refuse an obvious credential (fake AWS AKIA...EXAMPLE key, PEM private-key block, or a secret injected via str_replace new_str) with the canonical Refused: this appears to contain ... message, and the doc is never persisted. Ordinary prose that merely mentions "password" still writes (no false positive).
2. Read clamp: a body over the 64 KB budget comes back clamped with the [Truncated for display: ...] marker on both MCP channels (structuredContent.body + content[0].text), while the on-disk file keeps the full original bytes.

Tests

• e2e/mcp-contract.test.ts: the two test.skip entries replaced with real tests through the daemon /mcp transport (reusing the file's existing helpers). Uses clearly fake secret values only.
• e2e/memory-offline.test.ts: the same two behaviors at the CLI verb level - memory write of a secret exits non-zero with the canonical message; memory read of an oversized doc prints the clamped body + marker while the stored file stays whole.

Verification

• npm run build clean; mcp-contract + memory-offline run 3x each, all green; full offline set (35 tests) green; npm run verify green (incl. the local-server tools/list + instructions contract test on 0.0.3).
• Non-vacuous check: temporarily downgrading to 0.1.2/0.0.2 fails exactly the 4 new tests and passes the rest; restored 0.1.3/0.0.3 cleanly.